This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: R6 v/s R5 and Backward Compatibility ~Umberto Nongeroson 22.Jan.04 03:10 PM a Web browser Domino Designer All ReleasesWindows 2000
IBM makes every effort to see to it that applications developed in previous versions of Notes continue to work. You haven't described anything that fails to meet those criteria.
While you didn't say what it was that caused your LotusScript code to not compile, I suspect you ran into a conflict with a new reserved word or method name, such as NotesDocument.Lock. I'd like to point out that the code continued to work even though it was using a reserved word as a variable or subroutine or fieldname, whatever.
Expecting the code to recompile identically in Notes 6, goes beyond what IBM has committed to provide. What would you rather, given the choice: (1) have to rename a subroutine -- only if you have some other reason to edit the code -- because there's a new built-in function with the same name, or (2) not have the new built-in function available to use? I think there would be many more complaints from developers if IBM froze LotusScript at its current level of functionality, rather than adding anything that might prevent someone's code from recompiling. If you can suggest a way to avoid this dilemma, please do so!
As for your other problem, once again the code worked until you recompiled it, and once again I suspect your problem is a conflict with a new built-in function, property or method. Since you apparently didn't take the trouble to track down the error to the line it was occurring on, it's hard to say.